Add a GitHub Action for a container image build #169
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a GitHub Action for a container image build.
Currently, the container image is provided in a separate project git-developer/ti-cc-tool. I'd like to contribute it to this project.
The building blocks are:
Dockerfile
that contains the build instructions. By default, sources are taken from the local filesystem and all extra features are included. This can be configured by setting the build-argREPO_URL
(e.g. to an URL).run
shell script that allows firmware files as URL or local file, in native (bin/hex) and zipped format. It is used as entrypoint for the container image..github/workflows/image-build.yml
that starts the image build. It is currently configured to trigger a build on creation of a release (via the GitHub Web-UI) and additionally on pushes tomaster
. The image is created for several platforms in parallel (e.g.amd64
andarm/v7
) and uploaded to the GitHub package registry of this project.I created a release called demo-1 in my fork for you to get an impression what happens and how it looks like:
This PR probably needs some discussions and finetuning. Please add your comments so that we can elaborate on how it can be adapted to your requirements.
User documentation is not part of this PR yet. I suggest to merge the README of git-developer/ti-cc-tool with this project.